Systems and methods for port management in a network of moving things, for example including autonomous vehicles

ABSTRACT

Communication network architectures, systems and methods for supporting and/or effectively utilizing a network of mobile and/or static nodes. As a non-limiting example, various aspects of this disclosure provide communication network architectures, systems, and methods for supporting a dynamically configurable communication network comprising a complex array of both static and moving communication nodes (e.g., the Internet of moving things, autonomous vehicle networks, etc.). For example, a communication network, or one or more nodes thereof, implemented in accordance with various aspects of the present disclosure provide for efficient operation of distribution centers (e.g., ports, rail hubs, air freight hubs, etc.) that include networks of moving things. For example, in an example implementation, various aspects of the present disclosure provide systems and methods for efficiently controlling the operation of vehicles (e.g., boats, tugboats, ships, trucks, etc.) involved in port operations.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to, andclaims benefit from U.S. Provisional Patent Application Ser. No.62/429,480, filed on Dec. 2, 2016, and titled “Systems and Methods forPort Management in a Network of Moving Things,” which is herebyincorporated herein by reference in its entirety.

The present application is related to U.S. Provisional Application Ser.No. 62/221,997, titled “Integrated Communication Network for a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,016, titled “Systems and Methods for Synchronizing aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,066, titled “Systems and Methodsfor Monitoring a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,077, titled “Systems and Methodsfor Detecting and Classifying Anomalies in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,098, titled “Systems and Methods for Managing Mobility in aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,121, titled “Systems and Methods forManaging Connectivity a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,135, titled “Systemsand Methods for Collecting Sensor Data in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,145, titled “Systems and Methods for Interfacing with a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,150, titled “Systems and Methods for Interfacing with aUser of a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,183,titled “Systems and Methods for Vehicle Traffic Management in a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,186, titled “Systems and Methods for EnvironmentalManagement in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,190, titled “Systems and Methodsfor Port Management in a Network of Moving Things,” filed on Sep. 22,2015 and U.S. patent application Ser. No. 15/245,992, titled “Systemsand Methods for Shipping Management in a Network of Moving Things,”filed Aug. 26, 2016; U.S. Provisional Patent Application Ser. No.62/222,192, titled “Communication Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/244,828, titled“Utilizing Historical Data to Correct GPS Data in a Network of MovingThings,” filed on Oct. 22, 2015; U.S. Provisional Application Ser. No.62/244,930, titled “Using Anchors to Correct GPS Data in a Network ofMoving Things,” filed on Oct. 22, 2015; U.S. Provisional ApplicationSer. No. 62/246,368, titled “Systems and Methods for Inter-ApplicationCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/246,372, titled “Systems andMethods for Probing and Validating Communication in a Network of MovingThings,” filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015; U.S. Provisional Application Ser. No. 62/273,878,titled “Systems and Methods for Reconfiguring and Adapting Hardware in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/253,249, titled “Systems and Methods forOptimizing Data Gathering in a Network of Moving Things,” filed on Nov.10, 2015; U.S. Provisional Application Ser. No. 62/257,421, titled“Systems and Methods for Delay Tolerant Networking in a Network ofMoving Things,” filed on Nov. 19, 2015; U.S. Provisional ApplicationSer. No. 62/265,267, titled “Systems and Methods for Improving Coverageand Throughput of Mobile Access Points in a Network of Moving Things,”filed on Dec. 9, 2015; U.S. Provisional Application Ser. No. 62/270,858,titled “Channel Coordination in a Network of Moving Things,” filed onDec. 22, 2015; U.S. Provisional Application Ser. No. 62/257,854, titled“Systems and Methods for Network Coded Mesh Networking in a Network ofMoving Things,” filed on Nov. 20, 2015; U.S. Provisional ApplicationSer. No. 62/260,749, titled “Systems and Methods for Improving FixedAccess Point Coverage in a Network of Moving Things,” filed on Nov. 30,2015; U.S. Provisional Application Ser. No. 62/273,715, titled “Systemsand Methods for Managing Mobility Controllers and Their NetworkInteractions in a Network of Moving Things,” filed on Dec. 31, 2015;U.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016; U.S. ProvisionalApplication Ser. No. 62/268,188, titled “Captive Portal-related Controland Management in a Network of Moving Things,” filed on Dec. 16, 2015;U.S. Provisional Application Ser. No. 62/270,678, titled “Systems andMethods to Extrapolate High-Value Data from a Network of Moving Things,”filed on Dec. 22, 2015; U.S. Provisional Application Ser. No.62/272,750, titled “Systems and Methods for Remote Software Update andDistribution in a Network of Moving Things,” filed on Dec. 30, 2015;U.S. Provisional Application Ser. No. 62/278,662, titled “Systems andMethods for Remote Configuration Update and Distribution in a Network ofMoving Things,” filed on Jan. 14, 2016; U.S. Provisional ApplicationSer. No. 62/286,243, titled “Systems and Methods for Adapting a Networkof Moving Things Based on User Feedback,” filed on Jan. 22, 2016; U.S.Provisional Application Ser. No. 62/278,764, titled “Systems and Methodsto Guarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; and U.S. ProvisionalApplication Ser. No. 62/299,269, titled “Systems and Methods forAutomating and Easing the Installation and Setup of the InfrastructureSupporting a Network of Moving Things,” filed on Feb. 24, 2016; each ofwhich is hereby incorporated herein by reference in its entirety for allpurposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving mobile and static nodes. As anon-limiting example, current communication networks are unable toadequately support a network comprising a complex array of both movingand static nodes (e.g., the Internet of moving things, autonomousvehicle networks, etc.). For example, in a shipping port implementation,present systems fail to adequately support and/or control port operation(e.g., movement of trucks, boats, tugboats, ships, etc.) utilizing avariety of interconnected nodes of different types and functions,resulting in operational inefficiency. Limitations and disadvantages ofconventional methods and systems will become apparent to one of skill inthe art, through comparison of such approaches with some aspects of thepresent methods and systems set forth in the remainder of thisdisclosure with reference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows an example port environment, in accordance with variousaspects of the present disclosure.

FIG. 8 shows a flow diagram of example port operation, in accordancewith various aspects of the present disclosure.

FIG. 9 shows a block diagram of various components of an example networknode, in accordance with various aspects of the present disclosure.

SUMMARY

Various aspects of this disclosure provide communication networkarchitectures, systems and methods for supporting and/or effectivelyutilizing a network of mobile and/or static nodes. As a non-limitingexample, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings, autonomous vehicle networks, etc.). For example, a communicationnetwork, or one or more nodes thereof, implemented in accordance withvarious aspects of the present disclosure provide for efficientoperation of distribution centers (e.g., ports, rail hubs, air freighthubs, airports, etc.) that include networks of moving things. Forexample, in an example implementation, various aspects of the presentdisclosure provide systems and methods for efficiently controlling theoperation of vehicles (e.g., boats, tugboats, ships, trucks, etc.)involved in port operations.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10× the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, air freight hub, factory, plantation, mine, etc.)with many vehicles, machines and employees, a communication network inaccordance with various aspects of the present disclosure may expand thewireless coverage of enterprise and/or local Wi-Fi networks, for examplewithout resorting to a Telco-dependent solution based on SIM cards orcellular fees. In such an example scenario, apart from avoidingexpensive cellular data plans, limited data rate and poor cellularcoverage in some places, a communication network in accordance withvarious aspects of the present disclosure is also able to collect and/orcommunicate large amounts of data, in a reliable and real-time manner,where such data may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 (and/or network components) may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 200, 300, 400, 500-570, 600, 700, 800, and 900, discussedherein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplenetworks (and/or network components) 100, 300, 400, 500-570, 600, 700,800, and 900, discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample networks (and/or network components) 100, 200, 400, 500-570,600, 700, 800, and 900, discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 100, 200, 300, 500-570, 600, 700, 800, and 900, discussedherein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example networks (and/or network components) 100, 200, 300,400, 600, 700, 800, and 900, discussed herein. For example and withoutlimitation, any or all of the communication links (e.g., wired links,wireless links, etc.) shown in the example networks 500-570 aregenerally analogous to similarly positioned communication links shown inthe example network 100 of FIG. 1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 100, 200, 300, 400, 500-570, 700, 800, and 900, discussedherein. Notably, the example network 600 shows a plurality of Mobile APs(or OBUs), each communicatively coupled to a Fixed AP (or RSU), whereeach Mobile AP may provide network access to a vehicle network (e.g.,comprising other vehicles or vehicle networks, user devices, sensordevices, etc.).

Various aspects of the present disclosure will now be generallypresented in the context of a shipping port. For example, variousexample aspects of a shipping port system and/or network may be found inU.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, and U.S. patent application Ser. No. 15/245,992, titled“Systems and Methods for Shipping Management in a Network of MovingThings,” filed Aug. 26, 2016, each of which is hereby incorporatedherein by reference in its entirety for all purposes. It should beunderstood, however, that the particular details of the port context arefor demonstration purposes only and should not be construed as limitingthe scope of this disclosure. For example, the various aspects of thisdisclosure readily apply to other contexts (e.g., rail hubs, air freighthubs, airports, enterprise distribution centers, barge operations,etc.).

In a port environment, there may be many different entities (e.g.,enterprises, groups, fleets, etc.) operating in such environment. Forexample one or more entities may be responsible for shipping containers,one or more entities may be responsible for the trucks (e.g., containermovement, package shipping, people moving, etc.), one or more entitiesmay be responsible for the ships and/or boats (e.g., tugboats,crew/pilot shuttleboats, etc.), etc. There may also, for example, be ageneral port operator that oversees general port operations, acustomhouse that monitors and/or controls what enters/leaves a specificcountry, a security organization, etc.

Due to the interoperability between different stakeholders andproviders, the efficient and coordinated performance of port operationsis challenging. For example, inefficient and/or uncoordinated portoperation may result in entities losing control of containers, goods,operators, etc. Also for example, the services may be delayed, trucktraffic jams may occur inside and/or outside the port, goods may beinadequately secured and/or may be stolen. Additionally for example,relatively large amounts of money may be wasted. As an example, a portmay spend a large amount of money to contract truck services withoutunderstanding the present real-time needs of the port (e.g., containersper hour, etc.), which may change in real-time in response to any of avariety of causes or conditions (e.g., weather disruptions, accidents,traffic jams, vehicle mechanical failures, customhouse delays, etc.).Herein, various example challenges of port operation and managementthereof are presented (e.g., inside a port area, etc.).

Some of such challenges may, for example, result from a requirement ofself-contained communication systems over international waters and/orother communication regulations, which may render beneficial informationunavailable. For example, the lack of communication of various types ofbeneficial information may limit port management (e.g., withoutinformation of current exact ship locations, boat routes, travel time,etc.). Also for example, without data collection and analysis, it isdifficult if not impossible to understand patterns and to derive theinfluence of the weather/sea conditions, and also difficult if notimpossible to optimize vehicle (e.g., boats, trucks, etc.) routing andscheduling. The inability to optimize vehicle routing and schedulingmay, for example, decrease the port throughput, which may for example becharacterized in terms of ships or containers that enter/leave the portper day. Additionally for example, with little or no correlation betweenship and truck movement, it is very difficult to establish cargo truckrequirements to load and unload current docked ships and avoid waitingtimes for nearby ships ready to enter the port.

A smart port supported by a reliable communication network (e.g., avehicle communication system as discussed herein, for example with FixedAPs, Mobile APs carried by a variety of different types of vehicles,etc.) and real-time analytics, in accordance with various aspects ofthis disclosure, may experience substantially improved port managementand efficiency. Additionally, various aspects of this disclosure alsoprovide for accurate reporting and feedback. Further, various aspects ofthis disclosure enable the rendering of coordinated and collaborativedecisions and actions among port stakeholders in an automated fashion.Automatic invoicing may also be provided.

Various aspects of the present disclosure provide reliable positioninginformation (e.g., GPS positioning, wireless MAN or LAN triangulationpositioning, etc.), for example inside the operational area of a port.Also, various aspects of the present disclosure provide for themonitoring of boat movement, for example to determine travel times andimprove arrival/departure scheduling. Such scheduling may, for example,be based at least in part on current weather conditions. Additionally,various aspects of the present disclosure provide for the determinationof ship entrance time and estimated (or actual) parking time at ports,based at least in part on tugboat and/or passenger boat movements (e.g.,present location coordinates, velocity, travel direction, speed,intended route, etc.), previous patterns, etc. Further, various aspectsof the present disclosure provide or allow port activity management bycorrelating ship and cargo truck movement, which can allow a betterestimation of the costs to unload/load a ship, for example based on thenumber of trucks, time required to perform the loading and/or unloadingof the ship, etc.

Also, various aspects of the present disclosure provide for improvedtruck dispatch scheduling, for example according to ship docking times,the current number of ships waiting to enter the port, the number ofdocking places available in a port, etc. Additionally, various aspectsof the present disclosure provide for the measurement of towing timesand/or the time required for loading/unloading for automating invoicing(e.g., determining how much money the port authority has to pay to atruck company, how many trucks should be scheduled per day, etc.).Further various aspects of the present disclosure provide for securecommunication between most or all of the vehicles (e.g., passengerboats, tugboats, ships, trucks, cranes, personnel shuttles, etc.) insideports without having to involve third-party communication serviceproviders.

FIG. 7 shows an example port environment, in accordance with variousaspects of the present disclosure. The example environment 700 (ornetwork components thereof) may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 100, 200, 300, 400, 500-570, 600, 800, and 900, discussedherein. FIG. 8 shows a flow diagram 800 of example port operation, inaccordance with various aspects of the present disclosure. The exampleport operational flow 800 (or network components thereof) may, forexample, share any or all characteristics with the other examplenetworks (and/or network components) 100, 200, 300, 400, 500-570, 600,700, and 900, discussed herein. Various aspects of the presentdisclosure will now be presented in the example port operational contextand flow presented in FIGS. 7 and 8.

The example port environment 700 of FIG. 7 comprises an example DockZone served by a first Fixed AP (AP1) and a second Fixed AP (AP2). TheDock Zone may, for example, comprise an area for docking various typesof watercraft (e.g., boats for passenger transport (e.g., crew members,pilots, maintenance personnel, etc.), tugboats for towing ships in andout of the loading/unloading area, etc.). The first Fixed AP (AP1) andthe second Fixed AP (AP2) may, for example, communicate with each otherand/or with Mobile APs (or MAPs) in any vehicle within range (e.g., MAPsof passenger or shuttle boats, MAPs of tugboats, personal communicationdevices of dock workers, MAPs of trucks and/or other road vehicles, MAPsof trains, etc.). In the example port environment 700, the first FixedAP (AP1) is in wireless communication with a first boat B1(1), with thefirst boat B1(1) at a first location. Note that any of the boats (e.g.,the first passenger boat B1, the first tugboat T1, etc.) may be indirect wireless communication with each other. Also, the second Fixed AP(AP2) is in wireless communication with the first boat B1(2) at a secondlocation, with the first boat B1(3) at a third location, with a firsttugboat T1(1) at a first location, and with the first tugboat T1(6) at asixth location.

Though not shown in FIG. 7 for all of the Fixed APs (e.g., forillustrative clarity), any or all of the Fixed APs may be networked asshown in any of the example network configurations presented herein(e.g., with wireless connections, wireline connections, opticalconnections, etc.). For example, in the example illustration of FIG. 7,the links between AP1, AP7, and AP8 and the Cloud (e.g., a Private Cloudor network for port operations, a privatized portion of the publicCloud, etc.) are shown, but the links between AP2-AP6 and the Cloud arenot shown in FIG. 7 for illustrative clarity. For example, the Fixed APsmay provide communication pathways to Cloud servers, port networkcontrollers, a central port command center, etc.

The example port environment 700 may also comprise a Container Zone forthe temporary storage of shipping containers being loaded onto shipsand/or unloaded off from ships. The example Container Zone is covered byfour Fixed APs (AP3, AP4, AP5, and AP6). The Fixed APs (AP3, AP4, AP5,and AP6) may, for example, communicate with each other and/or withMobile APs in any vehicle within range (e.g., MAPs of passenger orshuttle boats, MAPs of tugboats, personal communication devices of dockworkers, MAPs of trucks or other road vehicles, MAPs of cranes, MAPs oftrains, MAPs of security vehicles, MAPs of ships, etc.). In the exampleport environment 700, the third Fixed AP (AP3) is in wirelesscommunication with a first truck TR1(2) at a second location, with thefirst tugboat T1(3) at a third location, and with the first tugboatT1(4) at a fourth location. The fourth Fixed AP (AP4) is in wirelesscommunication with the third truck TR3(2) at the second location. Also,the second truck TR2(2) at a second location is in wirelesscommunication with the first truck TR1(2) at the second location andwith the third truck TR3(3) at the second location. For example, thesecond truck TR2(2) at the second location can communicate with thethird Fixed AP (AP3) via the first truck TR1(2) at the second location.The first truck TR1(2) at the second location is also in wirelesscommunication with the first tugboat T1(3) at a third location. Forexample, the first tugboat T1(3) at the third location may communicatewith the third Fixed AP (AP3) directly and/or may communicate with thethird Fixed AP (AP3) through the first truck TR1(2) as the secondlocation.

The seventh Fixed AP (AP7) is in wireless communication with the firsttruck TR1(1) at a first location, with the second truck TR2(1) at afirst location, and with the third truck TR3(1) at a first location.Note that any or all of the trucks (TR1(1), TR2(1), and/or TR3(1)), orthe Mobile APs thereof, may be in direct communication with each other.The eighth Fixed AP (AP8) is in wireless communication with the firsttruck TR1(3) at a third location, with the second truck TR2(3) at athird location, and with the third truck TR3(3) at a third location.Note that any or all of the trucks (TR1(3), TR2(3), and/or TR3(3)), orthe Mobile APs thereof, may be in direct communication with each other.

Various aspects of the present disclosure may, for example, provide foranalyzing ship movement inside and outside the port area. Such shipmovement may, for example, be monitored and/or analyzed indirectly bymonitoring the movement of vehicles (e.g., passenger boats, tugboats,etc.) different from the ship. For example, various aspects of thepresent disclosure provide for monitoring and/or analyzing passengerboat travel time and/or scheduling. For example, at labels 1 and 9 inFIG. 7, the second Fixed AP (AP2) is in communication with the firstpassenger boat B1(2) as such boat is leaving the Dock Zone, and atlabels 2 and 10, the second Fixed AP (AP2) is in communication with thefirst passenger boat B1(3) as such boat is entering the Dock Zone. Whensuch communication is occurring, for example directly and/or indirectlythrough other Mobile APs, information regarding the first passenger boatB1 (e.g., location, velocity, orientation, attitude, shock, destination,time, operational health, fuel consumption, passenger load and/oridentification, etc.) may be collected from the first passenger boat B1and/or may be analyzed. Such passenger boats may, for example, bewaiting for ships to arrive to the port area (e.g., to shuttle pilots,crew, maintenance personnel, other passengers, etc.) and thus themovement of such passenger boats may be analyzed to derive that a shipis arriving to the port and/or leaving from the port.

Also for example, various aspects of the present disclosure provide formonitoring and/or analyzing tugboat travel time and/or scheduling. Forexample, at label 3 in FIG. 7, the second Fixed AP (AP2) is incommunication with the first tugboat T1(1) as such tugboat is leavingthe Dock Zone (e.g., to guide a ship into the port), and at label 8, thesecond Fixed AP (AP2) is in communication with the first tugboat T1(6)as such tugboat is entering the Dock Zone (e.g., upon completion oftowing a ship out of the port, upon completion of another task, etc.).Also for example, at label 4 in FIG. 7, the third Fixed AP (AP3) is incommunication with the first tugboat T1(3) as such tugboat is enteringthe ship unloading/loading zone (e.g., towing in a ship), and at label7, the third Fixed AP (AP3) is in communication with the first tugboatT1(7) as such tugboat is leaving the ship unloading/loading zone (e.g.,towing out a ship). When such communication is occurring, informationregarding the first tugboat T1 (e.g., location, velocity, destination,time, operational health, fuel consumption, towed load and/or towedvessel identification, task being presently performed, task justcompleted, etc.) may be collected from the first tugboat T1 and/or maybe analyzed. Such tugboats may, for example, be responsible for routinga cargo ship to and/or from a specific location with the port area, andthus the movement of such tugboats may be analyzed to derive that a shipis arriving to the port and/or leaving from the port.

Various aspects of the present disclosure may, for example, provide formonitoring, analyzing, and/or controlling truck utilization (ormovement) in and around the port area. For example, various aspects ofthe present disclosure provide for determining if and when ships areloading and/or unloading and how much time was spent performing suchloading/unloading. For example, while the ship is parked within the portarea, a set of trucks should be actively working near the place wherethe ship is parked. For example, at label 5 in FIG. 1, the first,second, and third trucks (TR1(1), TR2(1), and TR3(1)), which are incommunication with the seventh Fixed AP (AP7) and/or with each other,may be dispatched for performing loading/unloading operations for acargo ship. At a second position, the first, second, and third trucks(TR1(2), TR2(2), and TR3(2)), which are in communication with the thirdFixed AP (AP3) and/or the fourth Fixed AP (AP4) and/or with each other,may be working near the ship loading and/or unloading containers orcargo. At a third position, the first, second and third trucks, whichare in communication with the eighth Fixed AP (AP8) and/or with eachother may be leaving the area of the ship. The network may (e.g.,through the Fixed APs and/or Mobile APs, etc.), gather and processinformation of truck location, trajectory, route, velocity, operatorinformation, weight, fuel levels and/or consumption, emissions, etc.

The network may (e.g., through the Fixed APs and/or Mobile APs, etc.)monitor and/or provide truck metrics such as speed, distance, and fuelconsumption, operating temperature, etc., which may then, for example,be utilized for automatically making port management decisions, forautomatically making fleet recommendations, etc.

Various aspects of the disclosure may, for example, monitor vehicle(e.g., truck, boat, etc.) information in specific areas of the port(e.g., loading areas, parking areas, restricted areas, etc.). Examplesof such areas may, for example, include the Container Zone and/or DockZone in FIG. 7 and/or routes leading to/from such areas. For example,real-time problems with vehicles (e.g., vehicle malfunctioning,collisions, traffic jams, etc.) can be observed and managedautomatically, for example including dispatching of repair teams,halting superfluous vehicles that would worsen the traffic jam situationand waste fuel, etc.

Various aspects of the disclosure may also, for example, comprisecorrelating movement data between ships and trucks. For example, truckdispatch may be planned to optimize cargo ship loading/unloadingoperations. For example, in the example environment, informationregarding tugboat operation at label 4 (e.g., pulling the cargo ship S1into the loading/unloading location) and at label 5 (e.g., pulling thecargo ship S1 out of the loading/unloading location) may be utilized tocontrol the dispatch of trucks (indicated at label 5) to theloading/unloading location and/or may be utilized to control the recallof trucks (indicated at label 6) from the loading/unloading location.

Various aspects of the disclosure comprise methods and systems thatcollect vehicle positioning information (e.g., GPS information, etc.)and vehicle-related data through sensors and/or Mobile APs installed onport vehicles (e.g., passenger boats, tugboats, trucks, cranes, etc.),for example sampling their position periodically (e.g., every second,every ten seconds, every minute, etc.) and relaying such data usingwireless access points within reach, installed throughout the port(e.g., Fixed APs, Mobile APs, etc.). Utilizing a network in accordancewith various aspects of the present disclosure may, for example, providefor the avoidance of cellular device and/or network utilization,ensuring port autonomy and security regarding internal communicationrules, etc. The data may then, for example, be streamed (orcommunicated) to a platform (e.g., a Cloud platform or server, a localport control center, etc.), and/or stored for later analysis throughpattern discovery, and/or displayed in real time for interactive fleetmanagement procedures, non-limiting examples of which will now beprovided.

For example, various aspects of the present disclosure provide formanaging boat travel time and/or scheduling for ship arrival. Forexample, based on recent historical data about the boat positions andspeed, the system may determine/predict their average travel time. Atfirst, for example when there is no data available, predictions can bebased on manually collected data from surveys or internal port records.The system may, for example, determine if there is a sudden increase intrip duration, which may indicate bad weather/sea conditions. The systemmay then, for example, automatically make a recommendation to schedulenext trips earlier, for example to compensate for an anticipated delay.

Also for example, various aspects of the present disclosure provide forthe analysis of tugboat movement, for example to ascertain ship parkingtime and other port operational parameters. For example, based ongeo-fencing, the system can determine if tugboats and/or passenger boatsare entering or leaving the port. In an example implementation, it mightnot be possible to know the exact location of the cargo ships, but thesystem may utilize a state machine (or sequence flow) to model theinteraction process between various port vehicles and cargo ships. Forexample, referring to FIGS. 7 and 8, at label 1 of FIG. 7 and block 810of FIG. 8, a passenger boat B1 leaves the port to pick up a crew. Thepassenger boat B1 may also be carrying a pilot to the cargo ship S1. Thepassenger boat B1 may then return at label 2 of FIG. 7 and block 820 ofFIG. 8. At label 3 of FIG. 7 and block 830 of FIG. 8, a tugboat T1leaves the port to tow the cargo ship S1 inside the port and assist withmaneuvers, which is shown at label 4 of FIG. 7 and block 840 of FIG. 8.After the cargo ship S1 is loaded and/or unloaded, the tugboat T1 (or adifferent tugboat) assists the cargo ship S1 in leaving the port, whichis shown at label 7 of FIG. 7 and block 870 of FIG. 8, and then returnsto the dock, which is shown at label 8 of FIG. 7 and block 880 of FIG.8. The passenger boat then returns to the cargo ship S1 (e.g., toretrieve the pilot, bring crew back to the ship, etc.), which is shownat label 9 of FIG. 7 and block 890 of FIG. 8, and then returns to thedock, which is shown at label 10 of FIG. 7 and block 895 of FIG. 8. Thesequence of events, as monitored by the system, allows the system todetermine the parking time of the cargo ship S1 (e.g., by monitoring thetugboat T1 entering the port with the cargo ship S1 and leaving the portwith the cargo ship S1. Also for example, the system may determine thetime spent to perform all of the operations related to the ship S1(e.g., towing time, tugboat travel time, loading/unloading, pilot time,etc.), where such determined time may be utilized to automate invoicing.

Also for example, various aspects of the present disclosure provide forthe analysis of truck movement (e.g., communicating truck positioninformation, velocity information, route information, weightinformation, engine temperature information, engine emissioninformation, etc.), for example to determine whether ships areloading/unloading (e.g., correlating shipping throughput with truckservices). For example, as soon as a cargo ship docks in the port (or asa cargo ship is being towed into the port), trucks are dispatched tothat location to perform loading or unloading of its cargo. Given thatthe system knows the trucks positions, velocities, routes, speed, fuelconsumption, weight, operating temperature, etc., the system candetermine with precision if trucks arrive and leave the cargo ship'sarea with more or less load (e.g., see labels 5 and 6 of FIG. 7 and/orblocks 850 and 860 of FIG. 8). The difference in speed and fuelconsumption of the trucks may, for example, reveal the ship's currentloading/unloading state. For example, a truck with higher fuelconsumption and lower average speed (or acceleration or deceleration) islikely loaded, and a truck with lower fuel consumption and higheraverage speed (or acceleration or deceleration) is likely not loaded.

Additionally, the system can monitor the time that trucks spent insidethe loading/unloading area, traveling to/from the loading/unloadingarea, etc., which can then be analyzed for automating the invoicing forthe truck services.

By looking to the truck movements, the system can also manage the portoperation with regard to a new ship that wants to enter a port. Forexample, the system may determine that a cargo ship should wait outsidethe port for a time before entering, the cargo ship should park in aparticular other place to at least start loading/unloading itscontainers (e.g., different shipping processes may be performed inparallel). Though the current example process (e.g., state machinealgorithm, etc.) only shows serial docking/undocking operations, theprocess may also be expanded to parallel operations. For example, thevarious example blocks may be performed in parallel. Such operation mayalso, for example, be supplemented with the help of UAV/drones, whichmay also for example carry Mobile APs and be in communication with thenetwork of moving things.

Also for example, various aspects of the present disclosure provide forthe analysis of truck movement (e.g., communicating truck positioninformation, velocity information, route information, weightinformation, engine temperature information, engine emissioninformation, etc.), for example to optimize truck operation. Forexample, the system can leverage the vehicle network (e.g., Fixed APs,Mobile AP, etc.) to monitor (or determine) truck movement, for example,allowing the fleet management dashboard (e.g., a Cloud-based server, aport-based controller, etc.) to display how much time each truck hasspent stopped (e.g., with its engine on), moving slowly and/orintermittently, etc. The system may then analyze this information toestablish fuel consumption patterns and recommend policies (e.g., aschedule or real-time command for turning the engine off, etc.) that canresult in overall fuel savings. Note that any or all of the recommendedvehicle control functionality can be provided directly to the vehicle ofinterest (e.g., to an autonomous vehicle, to a smart yet manuallycontrol vehicle, etc.).

Additionally for example, various aspects of the present disclosureprovide for the planning of truck dispatching to optimize cargooperations. For example, by knowing (e.g., as discussed herein, etc.)when a cargo ship is preparing to enter the port, the fleet managementsystem can recommend the best time to dispatch trucks. For example,based on previous patterns (and also if it is known in advance how muchcargo the ship will unload), the system can also determine if the numberof trucks dispatched is adequate, that is, if there are too many or toofew trucks loading/unloading cargo. In an example implementation, thesystem may utilize third party web services to identify ships based onpublicly available information, for example to determine the ship'sidentification by cross referencing with external data historicaldetails may be provided.

Further for example, various aspects of the present disclosure provideport monitoring capability. For example, by detecting when vehiclesenter and leave specific areas (e.g., by information communicatedthrough the vehicle communication network) the port authorities maydetect rule infractions (e.g., parking in unauthorized areas, speedinfractions, traffic blocking infractions, accidents, etc.) and/or counthow many times trucks have entered the loading/unloading areas, amongother use cases. In addition, by defining speed limits for the differentareas of the port, the port authority may automatically detectover-speed infractions and issue notices with precise location, time andvehicle identification.

Additional example implementations illustrating various aspects of thepresent disclosure will now be provided. Note that such exampleimplementations are merely illustrative examples, and the scope of thisdisclosure is not limited by any particular characteristics of suchexample implementations.

An example implementation may, for example, include a system (or method)for controlling vehicle operation. The system may, for example, compriseat least one module that comprise a processor and memory (e.g., in asingle chip, in a single chassis, in a geographically distributedsystem, etc.). The at least one module may for example be operable to,at least: communicate with a mobile access point (MAP) on-board a firstvehicle to determine a status of the first vehicle, wherein the firstvehicle is a first type of port watercraft; determine a status of acargo ship based, at least in part, on the determined status of thefirst vehicle; and control operation of a second vehicle based, at leastin part, on the determined status of the cargo ship, wherein the secondvehicle is a second type of vehicle different from the first type ofport watercraft.

The MAP on-board the first vehicle may, for example, be operable toprovide wireless local area network (WLAN) connectivity services toclient devices around the first vehicle. The MAP may, for example, shareany or all characteristics with any of the mobile or fixed APs discussedherein.

The at least one module may, for example, be operable to determine thestatus of the cargo ship independent of any information received fromthe cargo ship. For example, various information about the cargo shipmight not be available to the at least one module (e.g., for securityreasons, legal reasons, wireless environment characteristics,communication incompatibilities, equipment failures, etc.).

The status of the first vehicle may comprise any one or more of thevehicle status (or context) parameters discussed herein. For example,the status of the first vehicle may comprise the location and/orvelocity of the first vehicle, the weight of the first vehicle, the fuellevel and/or fuel efficiency of the first vehicle, etc.

The first type of port watercraft may, for example, comprise a passengerboat. For example, the status of the passenger boat may comprisepassenger identity information. The first type of port watercraft may,for example comprise a tugboat. For example, the status of the tugboatmay comprise towing status (e.g., towing underway, towing preparationsbeing made, moving or not, speed, sea conditions being experienced,etc.).

The at least one module may, for example, be operable to, at leastcommunicate with a second MAP on-board a third vehicle to determine thestatus of the third vehicle, wherein the third vehicle is a third typeof port watercraft different from the first type of port watercraft; anddetermine the status of the cargo ship based also, at least in part, onthe determined status of the third vehicle. For example, the firstvehicle may comprise a passenger boat, and the third vehicle maycomprise a tugboat. Also, for example, the second vehicle may comprise atruck (e.g., a cargo truck, etc.), a crane, a forklift, a containerlift, etc., and the at least one module may be operable to controloperation of the second vehicle by, at least in part, operating todispatch and/or recall the second vehicle, schedule operation of thesecond vehicle, plan a travel route for the second vehicle, etc.

In another example implementation a system may be provided forcontrolling vehicle operation, where the system comprises: at least onemodule comprising a processor and memory. The at least one module may,for example, be operable to, at least: communicate with a mobile accesspoint (MAP) on-board a first vehicle operating in a first zone of a portto determine a status of the first vehicle; determine a status of asecond vehicle based, at least in part, on the determined status of thefirst vehicle, wherein the second vehicle is operating in a second zoneof the port that is independent of the first zone of the port; andcontrol operation of a third vehicle based, at least in part, on thedetermined status of the second vehicle, wherein the third vehicle isassociated with servicing the second vehicle.

The MAP on-board the first vehicle may, for example, be operable toprovide wireless local area network (WLAN) connectivity services toclient devices around the first vehicle. The MAP may, for example, shareany or all characteristics with any of the mobile and/or fixed APsdiscussed herein.

The first zone of the port may, for example, comprise a dock zone. Thethird vehicle may, for example, be associated with servicing the secondvehicle in a third zone of the port, independent of the first and secondzones. Such a third zone may, for example, comprise loading and/orunloading zone, a container storage zone, etc.

As discussed herein, the at least one module is operable to determinethe status of the second vehicle independent of any information receivedfrom the second vehicle.

Also, as discussed herein, the first vehicle may comprise a passengerboat, and the second vehicle may comprise a cargo ship. The status ofthe first vehicle may, for example, comprise passenger identityinformation. Additionally, as discussed herein, the first vehicle maycomprise a tugboat, and the second vehicle comprises a cargo ship.Further, as discussed herein, the first vehicle may comprise a passengerboat or a tugboat, the second vehicle may comprise a cargo ship, and thethird vehicle may comprise a cargo truck.

The at least one module may, for example, be operable to, at least:communicate with a second MAP on-board a fourth vehicle to determine thestatus of the second vehicle, wherein the fourth vehicle is a differenttype of vehicle than the first vehicle; and determine the status of thesecond based, at least in part, on the determined status of the firstvehicle and on the determined status of the fourth vehicle. For example,the first vehicle may comprise a passenger boat, and the fourth vehiclemay comprise a tugboat.

As discussed herein, the status of the first vehicle (or any vehicle)may comprise any or all of the status (or context) characteristicsdiscussed herein. For example, the status of the first vehicle maycomprise the location and/or velocity of the first vehicle.

The at least one module may, for example, be operable to controloperation of the third vehicle by, at least in part, operating todispatch and/or recall the third vehicle, schedule operation of thethird vehicle, develop a travel plan for the third vehicle, etc.

In yet another example implementation, a system (or method) may beprovided that comprises at least one module comprising a processor andmemory. The at least one module may, for example, be operable to, atleast: communicate with a mobile access point (MAP) on-board a firstvehicle to determine a status of the first vehicle, wherein the firstvehicle is a first type of vehicle determine a status of a secondvehicle based, at least in part, on the determined status of the firstvehicle and entirely independent of information from the second vehicle,wherein the second vehicle is a second type of vehicle different fromthe first type of vehicle; and control operation of a third vehiclebased, at least in part, on the determined status of the second vehicle,wherein the third vehicle is a third type of vehicle different from thefirst and second types of vehicles.

As discussed herein, the MAP may be operable to provide wireless localarea network (WLAN) connectivity services to client devices around thefirst vehicle. The MAP may, for example, share any or allcharacteristics with any of the mobile and/or fixed access pointsdiscussed herein.

The first, second, and third vehicles may, for example, be related toport operations. The at least one module may, for example, be operableto communicate with the MAP on-board the first vehicle when the firstvehicle is operating in a first zone of a port; determine the status ofthe second vehicle when the second vehicle is operating in a second zoneof the port that is independent of the first zone; and control operationof the third vehicle in a third zone of the port that is independent ofthe first and second zones. Also for example, the first vehicle is apassenger boat or a tugboat; the second vehicle is a cargo ship; and thethird vehicle is a cargo truck.

FIG. 9 shows a block diagram of various components of an example networknode, in accordance with various aspects of the present disclosure. Theexample node 900 may, for example, share any or all characteristics withthe other example methods, networks and/or network components 100, 200,300, 400, 500-570, 600, 700, and 800 discussed herein. For example, anyor all of the components of the example node 900 may perform any or allof the method steps presented herein.

The network node 900 may, for example, comprise any of the network nodesdiscussed herein, for example an access point (AP) node (e.g., a MobileAP, a Fixed AP, etc.), a Network Controller, a Cloud server and/ordatabase, a port operations controller, etc. The example node 900 maycomprise a variety of components (or modules), non-limiting examples ofwhich are provided herein.

The example node 900 may, for example, comprise a communicationinterface (I/F) module 920 (e.g., including a cellular communicationinterface module, mobile network communication interface module, Wi-Ficommunication interface module, user/client communication interfacemodule, etc.) that operates to perform any or all of the wireless and/orwired communication functionality for the node 900, many examples ofwhich are provided herein (e.g., communication with sensors external to(or of) the node 900, communication with the onboard diagnostic (OBD)system of a vehicle in which the node 900 is installed, communicationwith peer nodes, communication with Mobile APs and/or Fixed APs,communication with Network Controllers, communication with clientdevices, backhaul communication, Cloud server communication, etc.). Thecommunication interface (I/F) module 920 may, for example, operate inaccordance with any of a variety of cellular communication protocols,3G, 4G, LTE, wireless LAN communication protocols (e.g., Wi-Fi, etc.),wireless PAN communication protocols (e.g., Bluetooth, etc.), 802.11p orDSRC, satellite communication protocols, fiber or cable communicationprotocols, LAN protocols (e.g., Ethernet, etc.), TCP/IP, etc.

The example node 900 may, for example, comprise a Port OperationsControl Module (POCM) 930 that operates to perform any or all of theport operations control functionality (e.g., informationgathering/storing, information analysis, vehicle movement control,automated invoicing, etc.) discussed herein. The example POCM 930 may,for example, comprise hardware and/or software that operate to implementany or all of the node's POCM functionality discussed herein. Forexample, the POCM 930 may operate to perform any or all blocks of theexample method 800 of FIG. 8, operate to perform any or all of thefunctionality discussed with regard to the example environment 700 ofFIG. 7, any or all of the functionality discussed herein, etc.

The example node 900 may, for example, comprise a Master Control Module910 that generally manages operation of the node 900 at a high level.Such Master Control Module 910 may, for example, comprise variousaspects of an operating system for the node 900.

The example node 900 may further, for example, comprise one or moreapplications 950 executing on the node 900 (e.g., port operationmonitoring applications, port operation control applications, vehicledispatch control applications, vehicle movement monitoring application,security applications, invoicing applications, power managementapplications, location services applications, sensor interfaceapplications, etc.). Any or all of the applications may, for example,utilize (e.g., communicate with) the POCM 930 for any or all of the portcontrol functionality discussed herein. For example, any or all of theapplications may interact with the POCM 930 in any of the mannersdiscussed herein with regard to the example method 800 of FIG. 8, withregard to the example port environment 700 of FIG. 7, etc.

The example node 900 may also comprise one or more processors 980 andmemory devices 990. The processor(s) 980 may, for example, comprise anyof a variety of processor characteristics. For example, the processor(s)980 may comprise one or more of a general purpose processor, RISprocessor, microcontroller, ASIC, DSP, video processor, etc.). Thememory device(s) 990 may, for example comprise any of a variety ofmemory characteristics. For example, the memory device(s) 990 maycomprise a volatile memory, non-volatile memory, etc. The memorydevice(s) 990 may, for example, comprise a non-transitorycomputer-readable (or machine-readable) medium that comprises softwareinstructions that when executed by the processor(s) 980, cause the node900 (or modules or entities thereof) to perform any or all of thefunctionality discussed herein (e.g., with regard to the example methodsdiscussed herein, etc.). The memory device(s) 990 may, for example,store node information (e.g., neighbor node information, Wi-Fi hotspotlist information, NIB information, configurable cost functioninformation, port control information, port operational modelinformation, historical port operation information, port invoicinginformation, point vehicle control information, etc.). The memorydevice(s) 990 may also, for example, store any or all of the client listand/or topic list information discussed herein.

As explained herein, the functionality (e.g., POCM functionality, etc.)discussed herein may be performed in a single node, for example any orall of the nodes discussed herein, but may also be performed in adistributed manner in which respective portions of the functionalitydiscussed herein are performed by respective nodes.

A system implemented in accordance with various aspects of thisdisclosure allows reliable positioning and communication inside portswithout requiring external communication providers, for example byenabling a mesh network between tugboats, passenger boats, cargo trucks,etc. A low cost solution is provided for performing real-time monitoringand controlling. Such a system also provides automated invoicing. Forexample, by measuring loading/unloading times and towing times in animpartial way, the different entities involved with port operations(e.g., the port authority, truck operations, tugboat operations, shipoperations, etc.) can rely on a common system for providing reliable andtrustworthy operational metrics that are used for invoicing.

As discussed herein, an example implementation may include theutilization of unmanned aerial vehicles (UAV) or drones. For example,drones may be launched (e.g., by boat during crew pickup, etc.) toescort and provide ship positioning information (e.g., utilizing aMobile AP integrated into the UAV). Such an implementation maysubstantially enhance the prediction (or determination) of the shipcurrent location, as well as avoid installing GPS tracking devices onthe ship just for positioning inside the port. It should be noted thatany or all of the vehicles discussed herein may be autonomous (e.g.,including no on-board pilot or driver, etc.) or semi-autonomous (e.g.,including a human observer for at least most operation, for alloperation, etc.). For example, vehicle control may be performed bycommunicating with the autonomous control system of the vehicle.

Also, an example implementation may also provide for monitoring,analyzing, and understanding vehicle driver (or pilot) characteristics(e.g., driver riding time, fuel consumption per driver, driverefficiency, etc.).

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, and U.S. patent application Ser. No. 15/245,992, titled“Systems and Methods for Shipping Management in a Network of MovingThings,” filed Aug. 26, 2016, each of which is hereby incorporatedherein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide communicationnetwork architectures, systems and methods for supporting and/oreffectively utilizing a network of mobile and/or static nodes. As anon-limiting example, various aspects of this disclosure providecommunication network architectures, systems, and methods for supportinga dynamically configurable communication network comprising a complexarray of both static and moving communication nodes (e.g., the Internetof moving things, autonomous vehicle networks, etc.). For example, acommunication network, or one or more nodes thereof, implemented inaccordance with various aspects of the present disclosure provide forefficient operation of distribution centers (e.g., ports, rail hubs, airfreight hubs, airports, etc.) that include networks of moving things.For example, in an example implementation, various aspects of thepresent disclosure provide systems and methods for efficientlycontrolling the operation of vehicles (e.g., boats, tugboats, ships,trucks, etc.) involved in port operations.

While the foregoing has been described with reference to certain aspectsand examples, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted withoutdeparting from the scope of the disclosure. In addition, manymodifications may be made to adapt a particular situation or material tothe teachings of the disclosure without departing from its scope.Therefore, it is intended that the disclosure not be limited to theparticular example(s) disclosed, but that the disclosure will includeall examples falling within the scope of the appended claims.

What is claimed is:
 1. A system for controlling vehicle operation, the system comprising: at least one module comprising a processor and memory, the at least one module operable to, at least: communicate with a mobile access point (MAP) on-board a first vehicle to determine a status of the first vehicle, wherein the first vehicle is a first type of port watercraft; determine a status of a cargo ship based, at least in part, on the determined status of the first vehicle; and control operation of a second vehicle based, at least in part, on the determined status of the cargo ship, wherein the second vehicle is a second type of vehicle different from the first type of port watercraft.
 2. The system of claim 1, wherein the MAP on-board the first vehicle is operable to provide wireless local area network (WLAN) connectivity services to client devices around the first vehicle.
 3. The system of claim 1, wherein the at least one module is operable to determine the status of the cargo ship independent of any information received from the cargo ship.
 4. The system of claim 1, wherein the status of the first vehicle comprises the location and/or velocity of the first vehicle.
 5. The system of claim 1, wherein the first type of port watercraft comprises a passenger boat.
 6. The system of claim 5, wherein the status of the first vehicle comprises passenger identity information.
 7. The system of claim 1, wherein the first type of port watercraft comprises a tugboat.
 8. The system of claim 7, wherein the status of the first vehicle comprises towing status.
 9. The system of claim 1, wherein the at least one module is operable to, at least: communicate with a second MAP on-board a third vehicle to determine the status of the third vehicle, wherein the third vehicle is a third type of port watercraft different from the first type of port watercraft; and determine the status of the cargo ship based also, at least in part, on the determined status of the third vehicle.
 10. The system of claim 1, wherein the at least one module is operable to control operation of the second vehicle by, at least in part, operating to dispatch and/or recall the second vehicle.
 11. A system for controlling vehicle operation, the system comprising: at least one module comprising a processor and memory, the at least one module operable to, at least: communicate with a mobile access point (MAP) on-board a first vehicle operating in a first zone of a port to determine a status of the first vehicle; determine a status of a second vehicle based, at least in part, on the determined status of the first vehicle, wherein the second vehicle is operating in a second zone of the port that is independent of the first zone of the port; and control operation of a third vehicle based, at least in part, on the determined status of the second vehicle, wherein the third vehicle is associated with servicing the second vehicle.
 12. The system of claim 11, wherein the MAP on-board the first vehicle is operable to provide wireless local area network (WLAN) connectivity services to client devices around the first vehicle.
 13. The system of claim 11, wherein the first zone of the port comprises a dock zone of the port.
 14. The system of claim 11, wherein the third vehicle is associated with servicing the second vehicle in a third zone of the port, independent of the first and second zones.
 15. The system of claim 14, wherein the third zone comprises a loading/unloading zone of the port.
 16. The system of claim 11, wherein the at least one module is operable to determine the status of the second vehicle independent of any information received from the second vehicle.
 17. The system of claim 11, wherein the first vehicle comprises a passenger boat, and the second vehicle comprises a cargo ship.
 18. The system of claim 17, wherein status of the first vehicle comprises passenger identity information.
 19. The system of claim 11, wherein the first vehicle comprises a tugboat, and the second vehicle comprises a cargo ship.
 20. The system of claim 11, wherein the first vehicle comprises a passenger boat or a tugboat, the second vehicle comprises a cargo ship, and the third vehicle comprises a cargo truck.
 21. The system of claim 11, wherein the at least one module is operable to, at least: communicate with a second MAP on-board a fourth vehicle to determine the status of the second vehicle, wherein the fourth vehicle is a different type of vehicle than the first vehicle; and determine the status of the second based, at least in part, on the determined status of the first vehicle and on the determined status of the fourth vehicle.
 22. The system of claim 11, wherein the status of the first vehicle comprises the location and/or velocity of the first vehicle.
 23. The system of claim 11, wherein the at least one module is operable to control operation of the third vehicle by, at least in part, operating to dispatch and/or recall the third vehicle.
 24. A system for controlling vehicle operation, the system comprising: at least one module comprising a processor and memory, the at least one module operable to, at least: communicate with a mobile access point (MAP) on-board a first vehicle to determine a status of the first vehicle, wherein the first vehicle is a first type of vehicle; determine a status of a second vehicle based, at least in part, on the determined status of the first vehicle and entirely independent of information from the second vehicle, wherein the second vehicle is a second type of vehicle different from the first type of vehicle; and control operation of a third vehicle based, at least in part, on the determined status of the second vehicle, wherein the third vehicle is a third type of vehicle different from the first and second types of vehicles.
 25. The system of claim 24, wherein the MAP is operable to provide wireless local area network (WLAN) connectivity services to client devices around the first vehicle.
 26. The system of claim 24, wherein the first, second, and third vehicles are related to port operations.
 27. The system of claim 26, wherein the at least one module is operable to: communicate with the MAP on-board the first vehicle when the first vehicle is operating in a first zone of a port; determine the status of the second vehicle when the second vehicle is operating in a second zone of the port that is independent of the first zone; and control operation of the third vehicle in a third zone of the port that is independent of the first and second zones.
 28. The system of claim 26, wherein: the first vehicle is a passenger boat or a tugboat; the second vehicle is a cargo ship; and the third vehicle is a cargo truck. 